Share Restriction for Curated Playlists

ABSTRACT

Example techniques facilitate for applying a share restriction to a curated playlist within a shared playback queue. In example implementations, a first media playback system may share its playback queue with a second media playback system. The playback queue of the first media playback system may include a curated playlist associated with a share restriction. When sharing its playback queue of the first media playback system, the first media playback system may enforce the share restriction on the curated playlist as queued in a second playback queue of the second media playback system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional Patent application Ser. No. 16/174,703, filed on Oct. 30, 2018 entitled “Share Restriction for Curated Playlists,” which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/174,703 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional patent application Ser. No. 14/275,112, filed on May 12, 2014 entitled “Share Restriction for Media Items,” which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other items directed to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were severely limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The Sonos Wireless HiFi System enables people to experience music from virtually unlimited sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using the controller, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.

Given the ever growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:

FIG. 1 shows an example network configuration in which certain embodiments may be practiced;

FIG. 2 shows an example media playback system configuration;

FIG. 3 shows a functional block diagram of an example playback device;

FIG. 4 shows a functional block diagram of an example control device;

FIG. 5 shows an example controller interface;

FIG. 6 shows a flow diagram of an example method;

FIG. 7A shows a graphical representation of an example playback queue;

FIG. 7B shows a graphical representation of an example modified playback queue;

FIG. 8 shows a flow diagram of another example method;

FIG. 9 shows a flow diagram of an example method;

FIG. 10A shows a graphical representation of an example shared playback queue displayed in accordance with a share restriction;

FIG. 10B shows another graphical representation of a shared example playback queue displayed in accordance with a share restriction; and

FIG. 10C shows yet another graphical representation of a shared example playback queue displayed in accordance with a share restriction.

The drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Media services (e.g., Pandora® Radio, Spotify®, Slacker® Radio, Google Play™, iTunes Radio™, and others) are a popular source of media for playback on playback devices. Some media services may provide to their subscribers various sets of media items for addition to a “playback queue,” where the media items added to the playback queue may eventually be played back by a playback device. Such a set of media items may include particular media items in a particular order. In some instances, the set of media items and/or the particular order of the media items may be established by the media service itself, by one or more users of the media service, and/or by a third-party “curator” service, among other examples. For purposes of example and explanation herein, such a set of media items in a particular order may be referred to as a “playlist.”

In some implementations, it may be possible to share playback queues between playback devices and/or playback systems (i.e., systems of playback devices) via one or more networks. According to examples described herein, in a networked media playback configuration where a first user may share with a second user a playback queue that includes media items representative of a playlist, it may be desirable to apply a share restriction on some or all of the media items included in the playback queue. Such a share restriction may be used to limit access by the second user to some or all of the media items.

To enable sharing of playback queues in some instances, a network may communicatively couple a first and second media playback system, a first and second media service, and/or a media system server. In some implementations, the media system server may facilitate sharing media items between the media playback systems.

The media system server (or another suitable networked device) may be capable of “cross-service linking” shared media content. Cross-service linking may involve the media system server receiving from the first media playback system a share request that identifies a first media item that a first user would like to share with a second user of the second media playback system. The share request may also include an identifier of the to-be-shared media item that is unique to the first media service. When the second user does not have access to the first media item (e.g., because the second user does not have a subscription to the first media service), the media playback system may utilize a cross-service linking database to identify an associated media item provided by the second media service, where the second user does have a subscription to the second media service. Two media items may be associated when they include comparable underlying media content. The media playback system may then transmit to the second media playback system an identifier of the associated media item and thereby facilitate access of shared media content using the cross-service linking.

Nonetheless, cross-service linking may not be desirable in some instances. For example, as noted above, some media services and/or third-party curator services provide their subscribers media items representative of a playlist. A media service, subscriber to a media service, or a curator may have created a given set of media items representative of a playlist. Such a set of media items may include particular media items in a particular order based on the creator's preferences. As such, a given playlist may be proprietary to the source (e.g., creator) of the playlist. Accordingly, when a first user attempts to share with a second user a playback queue that includes media items representative of such a proprietary playlist, it may be undesirable for the media playback system to perform cross-service linking when the second user does not have a subscription with the creator of the playlist and/or does not have access to the media service that provides the media items that make up the playlist. It may generally be undesirable to allow unfettered sharing of playback queues for other reasons as well.

To help address this issue, when a first user attempts to share a playback queue that includes a plurality of media items representative of a proprietary playlist, a computing device (e.g., a playback device or control device) or a computing system (e.g., a cloud server) may determine one or more characteristics of the plurality of media items. One such characteristic may indicate a source of the plurality of media items (e.g., the media service and/or curator, among other examples). Based on the determined characteristics of the plurality of media items, the computing device or system may assign to the plurality of media items a share restriction, for example, because the plurality of media items is proprietary. The share restriction may limit access to the plurality of media items by a second computing device that is not associated with a subscription to the source of the plurality of media items.

The second computing device may then receive an indication of the share restriction and perhaps an indication of the playback queue that includes an indication of the plurality of media items. Thereafter, the second computing device may determine from the share restriction that the second computing device does not have access to the plurality of media items. Consequently, the second computing device may have limited or no playback ability with respect to plurality of the media items.

The second computing device may also be limited in other ways. As one example, the second computing device may be limited as to the extent to which a representation of the plurality of media items is displayed to the second user. For instance, the plurality of media items may be displayed such that it is grayed out and the media items are not selectable, or perhaps the plurality of media items may be replaced by an indication of where the user may obtain access to the plurality of media items. Other examples are also possible.

As indicated above, examples provided herein relate to a share restriction on a plurality of media items that is part of a playback queue. In one aspect, a method is provided. The method involves (a) receiving by a first computing device input data indicating an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In another aspect, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium having instructions stored thereon that are executable by a first computing device to cause the first computing device to perform functions, the functions include (a) receiving input data indicating an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In an example aspect, a method is provided. The method involves (a) receiving by a computing system from a first computing device an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In yet another example aspect, another method is provided. The method involves (a) receiving by a computing device (i) an indication of a shared playback queue, wherein the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items, (b) based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items, and (c) based at least on the determination that the computing device does not have access to the source of the plurality of media items, playing the shared playback queue in accordance with the share restriction.

In one other example aspect, an additional method is provided. The method involves (a) receiving by a computing device (i) an indication of a shared playback queue, wherein the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items, (b) based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items, and (c) based at least on the determination that the computing device does not have access to the source of the plurality of media items, causing a graphical display to display a representation of the plurality of media items in accordance with the share restriction.

It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments.

II. Example Network Configuration

FIG. 1 shows an example network configuration 100 in which one or more embodiments disclosed herein may be practiced or implemented. As shown, the network configuration 100 may include a media system server 102, two or more media playback systems 106 and 108, two or more media service servers 110 and 112, and a cloud network 114. In some examples, the media system server 102 may include a database 104. In other examples, the database 104 may be located on a different network element, perhaps one that is not shown. Accordingly, it should be understood that the network configuration 100 may include additional network elements as well.

The cloud network 114 may communicatively couple the various network elements of the network configuration 100. In such an arrangement, the media system server 102 may communicate with the media playback systems 106-108 and/or the media service servers 110-112 via the cloud network 114. Similarly, the media playback systems 106-108 may communicate with the media service servers 110-112 via the cloud network 114. Further, the media playback systems 106-108 may communicate with one another via the cloud network 114. The cloud network 114 may be, for example, a wide-area network (WAN). As such, the cloud network 114 may include the Internet and/or one or more cellular networks, among other networks.

Generally speaking, a media playback system 106-108 may be any type of media playback system configured to receive and transmit data over a data network and playback media items. Each of the media playback systems 106-108 may be physically located in different locations. Alternatively, the media playback systems 106-108 may be physically located in the same location (e.g., an office building). In practice, a media playback system 106-108 may include one or more playback devices. Such a media playback system is discussed in further detail below with reference to example media playback system 200.

A media service server 110-112 may include at least one processor, data storage, and a network interface, among other components. A media service server 110-112 may be configured to store media items (e.g., a media library) and/or access such media items to transmit to a playback device. A media service server 110-112 may also create or obtain metadata related to the media items, as well as store such metadata.

In practice, the media service servers 110-112 may provide media content to the media playback systems 106-108. In particular, each media service may provide streaming media and/or media downloads, among other examples. Each media service server may provide “Internet radio” service and/or “on-demand” service (e.g., where a user may request a particular media item) to one or both of the media playback systems 106-108. When a media service server 110-112 provides a media item to a media playback system, the media service server may provide metadata along with the media item.

The media system server 102 may include a network interface, a processing unit, and data storage, all of which may be communicatively linked together by a system bus, network, or other connection mechanism. The network interface may facilitate data flow between the media system server 102 and other network elements on the cloud network 114. The processing unit may include one or more general purpose processors and/or one or more special purpose processors and may be integrated in whole or in part with the network interface. The data storage may include a non-transitory computer-readable medium, such as optical, magnetic, or flash memory, and may be integrated in whole or in part with the processing unit. The data storage may then include program instructions that are executable by the processing unit to carry out various functions described herein.

In example implementations, the data storage may also include the database 104 that may contain data related to media items. The data may be stored in the form of a table or the like. In some implementations, the database 104 may include data that may be used by the media system server 102 to perform cross-service linking functions. Accordingly, the database 104 may be referred to herein as a “cross-service linking database.” In other examples, the media system server 102 may utilize an external database or the like to perform cross-service linking.

In general, cross-service linking involves the media system server 102 receiving a first media-item identifier of a first service provider and outputting a second media-item identifier of a second service provider, where the first media-item identifier and the second media-item identifier identify substantially the same underlying media content. In practice, each media service server 110-112 may maintain a respective database that includes media provided by the respective media service. And typically, each respective database may be maintained in a unique manner. As such, without using the cross-service linking database 104, information used to retrieve media from the media service server 110 may not be useful for retrieving media from the media service server 112. Accordingly, the cross-service linking database 104 may facilitate accessing media from a given media service (e.g., the media service server 112) using information related to a different media service (e.g., the media service server 110).

In example implementations, the media system server 102 may be configured to maintain the cross-service linking database 104, which may involve a number of functions. For example, the media system server 102 may receive a first message from the media playback system 106. For instance, after or while the media playback system 106 plays a first media item, the media playback system 106 may transmit the first message to the media system server 102. The first message may identify a first service (e.g., service provided by the media service server 110) used by the media playback system 106 to obtain the first media item for playback. The first message may also include a first service media-item identifier that the media service server 110 uses to identify the first media item. Further, the first message may include a first metadata that is associated with the first media item (e.g., a track title, artist name, album title, etc.). The media system server 102 may store some or all of this first message information in the cross-service linking database 104.

The media system server 102 may thereafter receive a second message from the media playback system 108. As with the first message, the second message may identify a second service (e.g., service provided by the media service server 112) used by the media playback system 108 to obtain a second media item for playback, a second service media-item identifier used to identify the second media item, and a second metadata that is associated with the second media item. The media system server 102 may store some or all of this second message information in the database 104.

The media system server 102 may then compare the second metadata with the first metadata that was previously stored in the database 104 to determine if, and to what extent, the first metadata and the second metadata have any similarities. If the media system server 102 determines that the second metadata and the first metadata are substantially similar, the media system server 102 may infer that the first media item and the second media item have comparable underlying media content. In response, the media system server 102 may store association data in the database 104 indicating that the first service media-item identifier and the second service media-item identifier identify media items that include the same content.

As a result of such an association, the media system server 102 may use the cross-service linking database 104 to retrieve the second service media-item identifier using the first service media-item identifier and vice versa. In practice, the media system server 102 may perform cross-service linking for a plurality of media items. In this way, a user who does not have access to a first service but does have access to a second service may still obtain desired media content from the second service using media-item information of the first service.

In some implementations, some or all of the cross-service linking functions described above may be carried out by any other suitable network element. Furthermore, in example implementations, one network element (e.g., the media system server 102) may perform cross-service linking functions to build the cross-service linking database, and then another network element (e.g., a computing device of either of the media playback systems 106, 108) may locally store and/or reference the cross-service linking database.

III. Example Media Playback System

FIG. 2 shows an example configuration of a media playback system 200. The media playback system 200 as shown is associated with an example home environment having several rooms and spaces, such as for example, a master bedroom, an office, a dining room, and a living room. As shown in the example of FIG. 2, the media playback system 200 includes playback devices 202-224, control devices 226 and 228, and a wired or wireless network router 230.

Further discussions relating to the different components of the example media playback system 200 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example media playback system 200, technologies described herein are not limited to applications within, among other things, the home environment as shown in FIG. 2. For instance, the technologies described herein may be useful in environments where multi-zone audio may be desired, such as, for example, a commercial setting like a restaurant, mall or airport, a vehicle like a sports utility vehicle (SUV), bus or car, a ship or boat, an airplane, and so on.

a. Example Playback Devices

FIG. 3 shows a functional block diagram of an example playback device 300 that may be configured to be one or more of the playback devices 202-224 of the media playback system 200 of FIG. 2. The playback device 300 may include a processor 302, software components 304, memory 306, audio processing components 308, audio amplifier(s) 310, speaker(s) 312, and a network interface 314 including wireless interface(s) 316 and wired interface(s) 318. In one case, the playback device 300 may not include the speaker(s) 312, but rather a speaker interface for connecting the playback device 300 to external speakers. In another case, the playback device 300 may include neither the speaker(s) 312 nor the audio amplifier(s) 310, but rather an audio interface for connecting the playback device 300 to an external audio amplifier or audio-visual receiver.

In one example, the processor 302 may be a clock-driven computing component configured to process input data according to instructions stored in the memory 306. The memory 306 may be a tangible computer-readable medium configured to store instructions executable by the processor 302. For instance, the memory 306 may be data storage that can be loaded with one or more of the software components 304 executable by the processor 302 to achieve certain functions. In one example, the functions may involve the playback device 300 retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device 300 sending audio data to another device or playback device on a network. In yet another example, the functions may involve pairing of the playback device 300 with one or more playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 300 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener will preferably not be able to perceive time-delay differences between playback of the audio content by the playback device 300 and the one or more other playback devices. U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference, provides in more detail some examples for audio playback synchronization among playback devices.

The memory 306 may further be configured to store data associated with the playback device 300, such as one or more zones and/or zone groups the playback device 300 is a part of, audio sources accessible by the playback device 300, or a playback queue that the playback device 300 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 300. The memory 306 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.

The audio processing components 308 may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In one embodiment, one or more of the audio processing components 308 may be a subcomponent of the processor 302. In one example, audio content may be processed and/or intentionally altered by the audio processing components 308 to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) 310 for amplification and playback through speaker(s) 312. Particularly, the audio amplifier(s) 310 may include devices configured to amplify audio signals to a level for driving one or more of the speakers 312. The speaker(s) 312 may include an individual transducer (e.g., a “driver”) or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) 312 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers 312 may be driven by an individual corresponding audio amplifier of the audio amplifier(s) 310. In addition to producing analog signals for playback by the playback device 300, the audio processing components 308 may be configured to process audio content to be sent to one or more other playback devices for playback.

Audio content to be processed and/or played back by the playback device 300 may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting 3.5 mm audio line-in connection) or the network interface 314.

The network interface 314 may be configured to facilitate a data flow between the playback device 300 and one or more other devices on a data network. As such, the playback device 300 may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device 300, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 300 may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 314 may be configured to parse the digital packet data such that the data destined for the playback device 300 is properly received and processed by the playback device 300.

As shown, the network interface 314 may include wireless interface(s) 316 and wired interface(s) 318. The wireless interface(s) 316 may provide network interface functions for the playback device 300 to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s) within a data network the playback device 300 is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wired interface(s) 318 may provide network interface functions for the playback device 300 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 314 shown in FIG. 3 includes both wireless interface(s) 316 and wired interface(s) 318, the network interface 314 may in some embodiments include only wireless interface(s) or only wired interface(s).

In one example, the playback device 300 and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device 300 may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as “bonded playback devices”) may further play audio content in synchrony with other playback devices.

In another example, the playback device 300 may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device 300 is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device 300 may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device 300, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device 300 renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in FIG. 3 or to the SONOS product offerings. For example, a playback device may include a wired or wireless headphone. In another example, a playback device may include or interact with a docking station for personal mobile media playback devices. In yet another example, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 200 of FIG. 2, the environment may have one or more playback zones, each with one or more playback devices. The media playback system 200 may be established with one or more playback zones, after which one or more zones may be added, or removed to arrive at the example configuration shown in FIG. 2. Each zone may be given a name according to a different room or space such as an office, bathroom, master bedroom, bedroom, kitchen, dining room, living room, and/or balcony. In one case, a single playback zone may include multiple rooms or spaces. In another case, a single room or space may include multiple playback zones.

As shown in FIG. 2, the balcony, dining room, kitchen, bathroom, office, and bedroom zones each have one playback device, while the living room and master bedroom zones each have multiple playback devices. In the living room zone, playback devices 204, 206, 208, and 210 may be configured to play audio content in synchrony as individual playback devices, as one or more bonded playback devices, as one or more consolidated playback devices, or any combination thereof. Similarly, in the case of the master bedroom, playback devices 222 and 224 may be configured to play audio content in synchrony as individual playback devices, as a bonded playback device, or as a consolidated playback device.

In one example, one or more playback zones in the environment of FIG. 2 may each be playing different audio content. For instance, the user may be grilling in the balcony zone and listening to hip hop music being played by the playback device 202 while another user may be preparing food in the kitchen zone and listening to classical music being played by the playback device 214. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office zone where the playback device 218 is playing the same rock music that is being playing by playback device 202 in the balcony zone. In such a case, playback devices 202 and 218 may be playing the rock music in synchrony such that the user may seamlessly (or at least substantially seamlessly) enjoy the audio content that is being played out-loud while moving between different playback zones. Synchronization among playback zones may be achieved in a manner similar to that of synchronization among playback devices, as described in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system 200 may be dynamically modified, and in some embodiments, the media playback system 100 supports numerous configurations. For instance, if a user physically moves one or more playback devices to or from a zone, the media playback system 200 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 202 from the balcony zone to the office zone, the office zone may now include both the playback device 218 and the playback device 202. The playback device 202 may be paired or grouped with the office zone and/or renamed if so desired via a control device such as the control devices 226 and 228. On the other hand, if the one or more playback devices are moved to a particular area in the home environment that is not already a playback zone, a new playback zone may be created for the particular area.

Further, different playback zones of the media playback system 200 may be dynamically combined into zone groups or split up into individual playback zones. For instance, the dining room zone and the kitchen zone 214 may be combined into a zone group for a dinner party such that playback devices 212 and 214 may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device 204, and a listening zone including playback devices 206, 208, and 210, if the user wishes to listen to music in the living room space while another user wishes to watch television.

c. Example Control Devices

FIG. 4 shows a functional block diagram of an example control device 400 that may be configured to be one or both of the control devices 226 and 228 of the media playback system 200. As shown, the control device 400 may include a processor 402, memory 404, a network interface 406, and a user interface 408. In one example, the control device 400 may be a dedicated controller for the media playback system 200. In another example, the control device 400 may be a network device on which media playback system controller application software may be installed, such as for example, an iPhone™, iPad™ or any other smart phone, tablet or network device (e.g., a networked computer such as a PC or Mac™).

The processor 402 may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 200. The memory 404 may be configured to store instructions executable by the processor 402 to perform those functions. The memory 404 may also be configured to store the media playback system controller application software and other data associated with the media playback system 200 and the user.

In one example, the network interface 406 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The network interface 406 may provide a means for the control device 400 to communicate with other devices in the media playback system 200. In one example, data and information (e.g., such as a state variable) may be communicated between control device 400 and other devices via the network interface 406. For instance, playback zone and zone group configurations in the media playback system 200 may be received by the control device 400 from a playback device or another network device, or transmitted by the control device 400 to another playback device or network device via the network interface 406. In some cases, the other network device may be another control device.

Playback device control commands such as volume control and audio playback control may also be communicated from the control device 400 to a playback device via the network interface 406. As suggested above, changes to configurations of the media playback system 200 may also be performed by a user using the control device 400. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device 400 may sometimes be referred to as a controller, whether the control device 400 is a dedicated controller or a network device on which media playback system controller application software is installed.

The user interface 408 of the control device 400 may be configured to facilitate user access and control of the media playback system 200, by providing a controller interface such as the controller interface 500 shown in FIG. 5. The controller interface 500 includes a playback control region 510, a playback zone region 520, a playback status region 530, a playback queue region 540, and an audio content sources region 550. The user interface 500 as shown is just one example of a user interface that may be provided on a network device such as the control device 400 of FIG. 4 (and/or the control devices 226 and 228 of FIG. 2) and accessed by users to control a media playback system such as the media playback system 200. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

The playback control region 510 may include selectable (e.g., by way of touch or by using a cursor) icons to cause playback devices in a selected playback zone or zone group to play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode. The playback control region 510 may also include selectable icons to modify equalization settings, and playback volume, among other possibilities.

The playback zone region 520 may include representations of playback zones within the media playback system 200. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface 500 are also possible. The representations of playback zones in the playback zone region 520 may be dynamically updated as playback zone or zone group configurations are modified.

The playback status region 530 may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 520 and/or the playback status region 530. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface 500.

The playback queue region 540 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.

Referring back to the user interface 500 of FIG. 5, the graphical representations of audio content in the playback queue region 540 may include track titles, artist names, track lengths, and other relevant information associated with the audio content in the playback queue. In one example, graphical representations of audio content may be selectable to bring up additional selectable icons to manage and/or manipulate the playback queue and/or audio content represented in the playback queue. For instance, a represented audio content may be removed from the playback queue, moved to a different position within the playback queue, or selected to be played immediately, or after any currently playing audio content, among other possibilities. A playback queue associated with a playback zone or zone group may be stored in a memory on one or more playback devices in the playback zone or zone group, on a playback device that is not in the playback zone or zone group, and/or some other designated device.

The audio content sources region 550 may include graphical representations of selectable audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. Discussions pertaining to audio content sources may be found in the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g. according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or more playback devices in a media playback system such as the media playback system 200 of FIG. 2, local music libraries on one or more network devices (such as a control device, a network-enabled personal computer, or a networked-attached storage (NAS), for example), streaming audio services providing audio content via the Internet (e.g., the media service servers 135-145), or audio sources connected to the media playback system via a line-in input connection on a playback device or network devise, among other possibilities.

In some embodiments, audio content sources may be regularly added or removed from a media playback system such as the media playback system 200 of FIG. 2. In one example, an indexing of audio items may be performed whenever one or more audio content sources are added, removed or updated. Indexing of audio items may involve scanning for identifiable audio items in all folders/directory shared over a network accessible by playback devices in the media playback system, and generating or updating an audio content database containing metadata (e.g., title, artist, album, track length, among others) and other associated information, such as a URI or URL for each identifiable audio item found. Other examples for managing and maintaining audio content sources may also be possible.

The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.

IV. Methods for Imposing Media-Item Share Restrictions

As discussed above, in some situations, it may be desirable to assign a share restriction to a plurality of media items to limit certain users' ability to access the plurality of media items.

For method 600 of FIG. 6, method 800 of FIG. 8, and method 900 of FIG. 9 and other processes and methods disclosed herein, the flowcharts show functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer-readable medium, for example, such as a storage device including a disk or hard drive. The computer-readable medium may include non-transitory computer-readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer-readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer-readable media may also be any other volatile or non-volatile storage systems. The computer-readable medium may be considered a computer-readable storage medium, for example, or a tangible storage device. In addition, for the method 600 and other processes and methods disclosed herein, each block in FIG. 6 may represent circuitry that is wired to perform the specific logical functions in the process.

Furthermore, although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

For clarity, the methods 600, 800, and 900 may be described herein with reference to FIGS. 7A-B and FIGS. 10A-C. It should be understood, however, that this is for purposes of example and explanation only and that the operations of the methods should not be limited by these figures.

1. First Example Method

The method 600 shown in FIG. 6 presents an embodiment of a method that may be implemented within the network configuration 100 by a playback device or control device (or a computing device running the media playback system controller application software discussed above) of one of the media playback systems 106-108. It should be understood that the method may be carried out in other suitable network configurations and/or by other suitable network elements as well. Method 600 may include one or more operations, functions, or actions as illustrated by one or more of blocks 602-608

The method 600 begins at block 602 with receiving by a first computing device input data indicating an instruction to share a playback queue, where the playback queue includes a plurality of media items. At block 604, the method 600 involves determining one or more characteristics of the plurality of media items, where at least one of the one or more characteristics indicates a source of the plurality of media items. At block 606, the method 600 involves, based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items. At block 608, the method 600 involves transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items. The blocks shown in FIG. 6 are discussed in further detail below.

a. Receiving Input Data Indicating Instruction to Share Playback Queue

The method 600 begins at block 602 with receiving by a first computing device input data indicating an instruction to share a playback queue, where the playback queue includes a plurality of media items. The first computing device may be a computing device of the media playback system 106. In some implementations, one or more functions may be performed before the first computing device receives the input data indicating the instruction to share the playback queue.

For example, before the first computing device receives such an input, the first computing device may receive one or more input data indicating an instruction to build the playback queue. A first user may have utilized a controller interface, such as the controller interface 500 of FIG. 5, to enter inputs indicating instructions to build the playback queue. FIG. 7A shows a graphical representation 700 of an example playback queue. As shown, the graphical representation 700 of the playback queue includes respective indicators of a plurality of media items 702 and respective indicators of additional media items 704.

As shown, the plurality of media items 702 may include particular media items, for example, media items C-H, that are in a particular order. The plurality of media items 702 may be representative of a playlist, which may have been created by the first media service, another subscriber of the first media service, or a third-party curator service, among other examples. In some implementations, the plurality of media items 702 may be proprietary to the creator of the plurality of media items. For example, the compilation of the individual media items and/or the order of the media items that make up the plurality of media items 702 may be copyrighted. As such, a subscription with the first media service and/or the third-party curator service (or perhaps an individual curator) may be required to access the plurality of media items 702.

The plurality of media items 702 may have been added to the playback queue in response to the first user selecting the plurality of media items 702 while using the controller interface 500 to access media provided by a first media service (e.g., media service provided by the media service server 110 of FIG. 1). The first user may subscribe to the first media service, and thus, the first computing device may be associated with the subscription such that the first computing device has access to the media provided by the first media service.

Alternatively, the plurality of media items 702 may have been added to the playback queue in response to the first user selecting the plurality of media items 702 while using the controller interface to access playlists provided by a third-party curator service. A third-party curator service may provide playlists created by a professional curator or perhaps a celebrity or the like. The first user may subscribe to the third-party curator service, and consequently, the first computing device may have access to playlists provided by the third-party curator.

In example implementations, a media service may provide curated playlists. That is, a curator may create playlists and allow the media service to provide the media items that make up the playlist. In such examples, to gain access to the playlists, a user may need a subscription to the media service or the curator, or perhaps both.

In any event, after the playback queue is built or selected (e.g., a playback queue may only include a plurality of media items representative of a playlist), the first computing device may receive the input data indicating the instruction to share the playback queue. For example, the first computing device may receive from the first user an input indicating that the first user would like to share the playback queue with another user. For instance, the first user may have selected “Share Queue” icon 706 to instruct the first computing device to share the playback queue represented in FIG. 7A. Although not shown, after the first user selected the “Share Queue” icon 706, the first user may have also identified to whom the playback queue should be shared with.

b. Determining One or More Characteristics of Plurality of Media Items

Returning back to FIG. 6, at block 604, the method 600 involves determining one or more characteristics of the plurality of media items, where at least one of the one or more characteristics indicates a source of the plurality of media items. In example implementations, the source of the plurality of media items may be a media service that provides the plurality of media items or a curator, among other examples.

In addition to one of the characteristics indicating a source of the plurality of media items, other characteristics are also possible. In general, the one or more characteristics indicate information that may reflect that the plurality of media items is proprietary and/or should not be shared without at least some limitation. Examples of other characteristics may include a total number of media items in the plurality of media items, artists of media items in the plurality of media items, and record labels that produced media items in the plurality of media items. Other examples are also possible.

In some examples, at least one of the one or more characteristics may indicate that credentials associated with the source of the plurality of media items are required to access the plurality of media items. For example, such a characteristic may indicate that a computing device should be associated with a subscription to the source (e.g., media service provider or curator) of the plurality of media items before accessing the plurality of media items. Additionally or alternatively, at least one of the one or more characteristics may include a restriction setting. The restriction setting may be configured to limit or perhaps prevent access to the plurality of media items when a computing device does not have subscription credentials. Other example characteristics are also possible.

Determining the one or more characteristics may be performed in a number of ways. In some examples, this determination may be based on metadata that is included with the plurality of media items. One or more of the media items of the plurality of media items may include metadata that identifies the source of the plurality of media items and/or any other information that indicates the above discussed other characteristics of the plurality of media items. The first computing device may use such metadata to determine the one or more characteristics.

In other examples, this function may additionally or alternatively involve the first computing device determining that the plurality of media items includes an access characteristic. The first computing device may have assigned the access characteristic to the plurality of media items when the plurality of media items was originally added to the playback queue. That is, in response to a user selecting a plurality of media items representative of a proprietary playlist, the first computing device may have assigned the access characteristic.

The access characteristic may operate to notify the first computing device that a share restriction may apply to the plurality of media items in the event that there is an attempt to share the plurality of media items with another computing device. As such, determining that the plurality of media items includes an access characteristic may cause the first computing device to perform further functions to determine other characteristics of the plurality of media items.

In yet other examples, determining the one or more characteristics may additionally or alternatively involve the first computing device referencing a server that stores a database of proprietary playlists. The first computing device may communicate with such a server via the cloud network 114. In some examples, the first computing device (or perhaps the server itself) may determine whether the playback queue includes particular media items in a particular order that match any of the proprietary playlists stored in the database. In other examples, where the plurality of media items includes an access characteristic, the first computing device may determine whether the plurality of media items match any of the proprietary playlists stored in the database. In the event that the first computing device determines that such a match exists, the first computing device may then determine the source, any restriction settings, etc. of the matching proprietary playlist. Other examples of determining the one or more characteristics of the plurality of media items are also possible.

c. Assigning to Plurality of Media Items a Share Restriction

At block 606, the method 600 involves, based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items. For example, based on the source of the plurality of media items and/or any of the other above-discussed determined characteristics, the first computing device may assign to the plurality of media items the share restriction to limit access to the plurality of media items by computing devices that do not subscribe to the source of the plurality of media items, such as a computing device of the media playback system 108.

In some examples, the share restriction may be an indicator indicating that access to the plurality of media items is limited when a computing device does not subscribe to the source of the plurality of media items or a media service the provides the plurality of media items. The share restriction may be included in metadata that is included with the plurality of media items. In other examples, the share restriction may be a mechanism that prevents access to the plurality of media items when a computing device does not subscribe to the source and/or a provider of the plurality of media items. For instance, such a share restriction may operate to encrypt the plurality of media items such that credentials associated with the source and/or a provider of the plurality of media items are required to access them. Other examples of a share restriction are possible.

The share restriction may include one or more different types of restrictions that limit access to the plurality of media items by non-subscribing computing devices, such as a computing device of the media playback system 108. The share restriction may include a display restriction that limits the display of the plurality of media items by the second computing device. The display restriction may limit the extent to which the second computing device is able to display the plurality of media items or the display restriction may prevent the second computing device from being able to display the plurality of media items altogether.

Additionally or alternatively, the share restriction may include a playback restriction that limits the playback of the plurality of media items by non-subscribing computing devices. The playback restriction may limit the extent to which the second computing device is able to playback the plurality of media items. For example, the playback restriction may limit the playback of the plurality of media items by the second computing device to a portion of one or more of the media items. In another example, the playback restriction may allow playback of the media items but may play an audio and/or visual advertisement during playback of one or more of the media items. The advertisement may be associated with the source of the plurality of media items and/or may provide information to the second user regarding how to obtain full access to the plurality of media items (e.g., by subscribing to the source of the plurality of media items). The playback restriction may alternatively prevent playback of the plurality of media items by the second computing device altogether. Other examples are possible as well.

d. Transmitting Indication of Share Restriction

At block 608, the method 600 involves transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items. The first computing device may transmit to the second computing device (e.g., a computing device of the media playback system 108) the indication of the share restriction via the cloud network 114. The first computing device may transmit the indication of the share restriction directly to the second computing device, or the first computing device may transmit the indication of the share restriction indirectly to the second computing device via the media system server 102.

In any event, in some examples, the indication of the share restriction may take the form of a restriction message that identifies the media items that the share restriction applies to. The restriction message may also identify the extent of the share restriction (e.g., whether the share restriction includes a display and/or playback restriction), and/or a media or curator service subscription that may avoid the share restriction (e.g., a subscription to the source and/or a provider of the plurality of media items or perhaps a subscription to a companion service).

In other examples, the indication of the share restriction may be transmitted along with an indication of the playback queue. The indication of the playback queue may include respective indications of the plurality of media items and of any additional media items included in the playback queue. Alternatively, the indication of the playback queue may include respective indications for each media item of the playback queue. In such an example, the indication of the share restriction may be sent as a separate message (e.g., similar to the above-discussed restriction message), or perhaps the indication of the share restriction may be included in metadata that is included with the respective indications of the media items of the playback queue.

In any event, the indication of the share restriction may be operable to cause the second computing device to have limited access to the plurality of media items. In this way, the share restriction may facilitate maintaining the proprietary nature of the plurality of media items.

e. Additional Functions

Although not shown in FIG. 6, additional functions may be carried out with or in addition to method 600. For example, after the first computing device assigns the plurality of media items the share restriction, the first computing device may receive input data indicating a modification of the plurality of media items. For instance, after the first user added the plurality of media items to the playback queue, the first user may then use the controller interface 500 to modify the plurality of media items.

To illustrate, FIG. 7B shows a graphical representation 708 of an example modified playback queue. As shown, the plurality of media items 702 from FIG. 7A has been modified (for clarity, the original media items from the plurality of media items 702 are bolded). A modification may include removing one or more of the plurality of media items (e.g., “Media Item H” is shown as removed from the plurality of media items), adding one or more additional media items (e.g., “Media Item K” is shown as added to the plurality of media items), and/or reordering one or more of the plurality of media items (e.g., “Media Item E” and “Media Item G” are shown as reordered). Other example modifications are possible.

Based at least on the modification to the plurality of media items, the first computing device may remove the share restriction from the plurality of media items. In this way, the first user may freely share the playback queue, where the media items in the playback queue have been sufficiently modified.

In some examples, removing the share restriction may first involve the first computing device determining that the plurality of media items has been modified beyond a predetermined modification threshold. In practice, this function may involve the first computing device maintaining a modification count and updating the modification count for each modification that is made to the plurality of media items. As the modification count is updated, the first computing device may compare the modification count to the predetermined modification threshold. The modification threshold may include a predetermined number of media items removed, a predetermined number of media items added, a predetermined degree of reordering of media items, or a predetermined total number of modifications, among other possibilities.

In some examples, certain modifications may be weighted differently. For example, removing a media item may be weighted more than reordering a media item, which itself may be weighted more than adding a media item. Other examples of relative weights are also possible.

When the first computing device determines that the plurality of media items has been modified beyond the predetermined modification threshold, the first computing device may remove the share restriction. In this respect, the first computing device may be configured to make a determination as to when modifications cause a set of media items to no longer resemble the plurality of media items that is proprietary.

2. Second Example Method

The method 800 shown in FIG. 8 presents an embodiment of a method that may be implemented within the network configuration 100 by the media system server 102. It should be understood that the method may be carried out on other suitable network configurations and/or by other suitable network elements as well. The method 800 may include one or more operations, functions, or actions as illustrated by one or more of blocks 802-808.

The method 800 begins at block 802 with receiving by a computing system from a first computing device an instruction to share a playback queue, where the playback queue includes a plurality of media items. At block 804, the method 800 involves determining one or more characteristics of the plurality of media items, where at least one of the one or more characteristics indicates a source of the plurality of media items. At block 806, the method 800 involves, based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items. At block 808, the method 800 involves transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items. The blocks shown in FIG. 8 are discussed in further detail below.

a. Receiving Instruction to Share Playback Queue

The method 800 begins at block 802 with receiving by a computing system from a first computing device an instruction to share a playback queue, where the playback queue includes a plurality of media items. For example, the media system server 102 may receive the instruction to share the playback queue from a first computing device of the media playback system 106 via the cloud network 114. The first computing device may have transmitted to the media system server 102 the instruction after receiving input data indicating the instruction to share the playback queue. The first computing device may have received the input data in the same or a similar manner as discussed above with reference to block 602 of FIG. 6.

The instruction to share the playback queue may include an indication of the playback queue. Broadly speaking, the indication of the playback queue may be used by the media system server 102 to identify and/or locate media items of the playback queue. The playback queue may be the same as or similar to the playback queue discussed above.

In some examples, the indication of the playback queue may include an indication of the plurality of media items. Such an indication may be an indicator specific to a particular media or curator service that may be used to retrieve the plurality of media items. For example, the indicator may be a pointer or the like to the plurality of media items, such as a URI or URL. In other examples, the indication of the plurality of media items may include respective indicators for each of the media items of the plurality of media items that may be used to retrieve the media items individually. In example implementations, the indication of the playback queue may also include respective indicators of one or more additional media items included in the playback queue. Such indicators may operable to locate in the network configuration 100 the one or more additional media items. For example, the indicators may be media-item pointers or the like that identify respective network locations of the additional media items.

The instruction to share the playback queue may also include an identifier of an intended recipient of the shared playback queue. Such an identifier may identify a user to whom the playback queue should be shared with. Based on the identifier, the media system server 102 may be configured to determine a network location, such as an IP address, of a computing device associated with the user. In other examples, the identifier of the intended recipient of the shared playback queue may itself identify the location of the computing device associated with the user. Other examples are also possible.

b. Determining One or More Characteristics of Plurality of Media Items

At block 804, the method 800 involves determining one or more characteristics of the plurality of media items, where at least one of the one or more characteristics indicates a source of the plurality of media items. This function may be performed in a similar manner as discussed above with reference to block 604 of FIG. 6.

c. Assigning to Plurality of Media Items a Share Restriction

At block 806, the method 800 involves, based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items. This function may be performed in a similar manner as discussed above with reference to block 606 of FIG. 6.

d. Transmitting Indication of Share Restriction

At block 808, the method 800 involves transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items. The media system server 102 may transmit to the second computing device (e.g., a computing device of the media playback system 108) the indication of the share restriction via the cloud network 114. The share restriction may be the same as or similar to the share restriction discussed above with reference to block 608 of FIG. 6. The media system server 102 may also transmit to the second computing device an indication of the playback queue, which may be the same as or different to the indication of the playback queue from block 802.

Although not shown in FIG. 8, additional functions may be carried out with or in addition to method 800. The media system server 102 may be configured to perform additional functions similar to those discussed above with reference to FIG. 6.

V. Methods for Implementing Media-Item Share Restrictions

In some implementations, after a media-item share restriction is imposed on a plurality of media items of a playback queue, a computing device may receive an indication of a share restriction assigned to the plurality of media items. Thereafter, the computing device may attempt to access the plurality of media items, and in some situations, the computing device may be limited or prevented from such access.

The method 900 shown in FIG. 9 presents an embodiment of a method that may be implemented within the network configuration 100 by a playback device or control device (or a computing device running the media playback system controller application software discussed above) of one of the media playback systems 106-108. It should be understood that the method may be carried out on other suitable network configurations and/or by other suitable network elements as well. The method 900 may include one or more operations, functions, or actions as illustrated by one or more of blocks 902-908.

The method 900 begins at block 902 with receiving by a computing device (i) an indication of a shared playback queue, where the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items. At block 904, the method 900 involves, based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items. In certain implementations, at block 906, the method 900 involves, based at least on the determination that the computing device does not have access to the source of the plurality of media items, causing a graphical display to display a representation of the plurality of media items in accordance with the share restriction. In other implementations, the method 900 may additionally or alternatively involve, at block 908, based at least on the determination that the computing device does not have access to the source of the plurality of media items, playing the shared playback queue in accordance with the share restriction. The blocks shown in FIG. 9 are discussed in further detail below.

a. Receiving Shared Playback Queue and Indication of Share Restriction Assigned to Plurality of Media Items

The method 900 begins at block 902 with receiving by a computing device (i) an indication of a shared playback queue, where the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items. In some examples, the shared playback queue may only include a plurality of media items and thus, the indication of the shared playback queue may not include an indication of one or more additional media items.

The computing device may be a computing device of the media playback system 108. The computing device may have received the indication of the shared playback queue and the indication of the share restriction from a computing device of the media playback system 106 (e.g., after block 608 of FIG. 6) and/or the media system server 102 (e.g., after block 808 of FIG. 8). The indication of the shared playback queue and the indication of the share restriction may be the same as or similar to the indications and/or indicators discussed above.

b. Determining Computing Device does not have Access

At block 904, the method 900 involves, based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items. This function may be performed a number of manners.

In some examples, this function may first involve the computing device determining whether the computing device is associated with a subscription to a media service provider and/or curator associated with the share restriction. For instance, the share restriction may identify that a subscription to a first media service and/or curator is required to access the plurality of media items. The computing device may use the share restriction to determine whether it is associated with such a subscription. When the computing device determines that it is not associated with such a subscription, the computing device may in turn determine that it does not have access to the source and/or curator of the plurality of media items.

In examples where the share restriction indicates that non-subscribing users have limited access to the plurality of media items, after the computing device determines that it is not associated with an appropriate subscription, the computing device itself may impose any access restriction in accordance with the share restriction. In other examples where the share restriction is configured to prevent non-subscribing users from accessing the plurality of media items, it may be unnecessary for the computing device to determine whether it is associated with an appropriate subscription. This may be because the share restriction itself may limit the computing device's ability to access the plurality of media items.

After block 904, as indicated by the dashed lines, the method 900 may involve either the block 906 or 908, or perhaps both. That is, the method 900 need not involve both of the blocks 906 and 908, but in some implementations the method 900 may include both.

c. Causing Graphical Display to Display in Accordance with Share Restriction

In certain implementations, at block 906, the method 900 involves, based at least on the determination that the computing device does not have access to the source of the plurality of media items, causing a graphical display to display a representation of the plurality of media items in accordance with the share restriction. Such a representation may be shown on a controller interface, such as the controller interface 500.

In some examples, before this function is performed, the computing device may use the share restriction to determine one or more display parameters for the plurality of media items that limit the display of the plurality of media items. The one or display parameters may control if and to what extent the plurality of media items are displayed. For example, the display parameters may gray out the plurality of media item and/or cause the plurality of media items to not be selectable. Alternatively, the display parameters may block out the plurality of media items altogether. Based at least on the determination that the computing device does not have access to the source of the plurality of media items, the computing device may cause the graphical display to display the representation of the plurality of media items in accordance with one or more display parameters.

To illustrate, FIGS. 10A-C show example graphical representations of an example shared playback queue displayed in accordance with a share restriction. Such representations may be a result of the first user sharing the playback queue shown in FIG. 7A.

As shown in FIG. 10A, a graphical representation 1000 of a shared playback queue includes a graphical representation 1002 of the plurality of media items and a graphical representation 1004 of additional media items. In this example, the graphical representation 1004 of the additional media items includes respective media-item identifiers for the additional media items that are selectable, while the graphical representation 1002 of the plurality of media items includes respective media-item identifiers for the plurality of media items that are not selectable. In some examples, selecting a selectable media-item identifier may cause the computing device to playback the corresponding media item. Furthermore, the graphical representation 1002 of the plurality of media items displays the respective media-item identifiers as grayed out.

FIG. 10B shows another graphical representation 1006 of the shared playback queue that includes the graphical representation 1004 of the additional media items from FIG. 10A and a graphical representation 1008 of the plurality of media items. As shown, the graphical representation 1008 includes an indication that the plurality of media items is not accessible as well as an indication 1010 of a source of the plurality of media items from which access to the plurality of media items may be obtained. In this example, the indication 1010 of the source is selectable and may hyperlink to a webpage associated with the source of the plurality of media items where a user may create an account and thereby subscribe to the source (e.g., a media service and/or curator).

FIG. 10C shows yet another graphical representation 1012 of the shared playback queue that includes the graphical representation 1004 of the additional media items from FIG. 10A. In this example, the representation of the plurality of media items in accordance with the share restriction is a null representation. As such, the second user may be unaware of the fact that the first user attempted to share the plurality of media items.

It should be understood that FIGS. 10A-10C are only a few possible examples of graphical representations of a shared playback queue displayed in accordance with a share restriction and that such figures are shown for purposes of example and explanation and should not be construed as limiting. Various other representations are possible.

d. Playing Shared Playback Queue in Accordance with Share Restriction

Returning back to FIG. 9, in example implementations, the method 900 may additionally or alternatively involve, at block 908, based at least on the determination that the computing device does not have access to the source of the plurality of media items, playing the shared playback queue in accordance with the share restriction. In some examples, the computing device itself may play the shared playback queue in accordance with the share restriction. In other examples, the computing device may cause another device, such as a playback device of the media playback system 108, to play the shared playback queue in accordance with the share restriction.

In some examples, before this function is performed, the computing device may use the share restriction to determine one or more playback parameters for the plurality of media items that limit the playback of the plurality of media items. The one or display parameters may control if and to what extent a computing device may play the plurality of media items. For example, the playback parameters may limit the playback to samples of the plurality of media items (e.g., a predefined duration of playback, such as 20 seconds) and/or insert advertisements associated with the source of the plurality of media items into each of the media items. In other examples, the playback parameters may prevent the playback of the plurality of media items altogether. Based at least on the determination that the computing device does not have access to the source of the plurality of media items, the computing device may play the plurality of media items in accordance with one or more playback parameters.

In practice, playing the shared playback queue in accordance with the share restriction may involve playing the one or more additional media items and not playing the plurality of media items. Alternatively, this function may involve playing a sample of one or more of the media items of the plurality of media items. Additionally or alternatively, this function may involve playing the plurality of media items along with advertisements associated with the source of the plurality of media items. Other examples of playback in accordance with the share restriction are also possible.

VI. Conclusion

The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.

As discussed above, the examples provided herein relate to a share restriction on a plurality of media items that is part of a playback queue. In one aspect, a method is provided. The method involves (a) receiving by a first computing device input data indicating an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In another aspect, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium having instructions stored thereon that are executable by a first computing device to cause the first computing device to perform functions, the functions include (a) receiving input data indicating an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In an example aspect, a method is provided. The method involves (a) receiving by a computing system from a first computing device an instruction to share a playback queue, wherein the playback queue comprises a plurality of media items, (b) determining one or more characteristics of the plurality of media items, wherein at least one of the one or more characteristics indicates a source of the plurality of media items, (c) based on the determined one or more characteristics of the plurality of media items, assigning to the plurality of media items a share restriction that limits access to the plurality of media items, and (d) transmitting to a second computing device an indication of the share restriction assigned to the plurality of media items.

In yet another example aspect, another method is provided. The method involves (a) receiving by a computing device (i) an indication of a shared playback queue, wherein the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items, (b) based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items, and (c) based at least on the determination that the computing device does not have access to the source of the plurality of media items, playing the shared playback queue in accordance with the share restriction.

In one other example aspect, an additional method is provided. The method involves (a) receiving by a computing device (i) an indication of a shared playback queue, wherein the indication of the shared playback queue includes at least an indication of a plurality of media items and an indication of one or more additional media items, and (ii) an indication of a share restriction assigned to the plurality of media items, (b) based on the share restriction, determining that the computing device does not have access to a source of the plurality of media items, and (c) based at least on the determination that the computing device does not have access to the source of the plurality of media items, causing a graphical display to display a representation of the plurality of media items in accordance with the share restriction.

Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware. 

1. A method to be performed by a first media playback system, the method comprising: receiving, via a network interface of the first media playback system from a mobile device, data representing an instruction to queue a curated playlist of audio tracks to a first playback queue for playback via one or more first playback devices of the first media playback system, wherein the first playback queue defines a playback sequence for media items in the first playback queue, wherein a first user account of a first cloud service is associated with the first media playback system, wherein the curated playlist of audio tracks consists of a proprietary set of audio tracks defined and arranged into a particular sequence by the first cloud service, and wherein the audio tracks of the curated playlist are streamable from one or more servers of a second cloud service; based on receiving the data representing an instruction to queue the curated playlist of audio tracks to the first playback queue, adding, via the first media playback system, respective representations of each audio track within the curated playlist to the first playback queue, wherein the first playback queue is maintained in data storage of the one or more first playback devices, and wherein the respective representations of each audio track within the curated playlist indicate respective network locations of each audio track at the one or more servers of the second cloud service; receiving, via the network interface of the first media playback system, data indicating an instruction to share the first playback queue with a second media playback system that comprises one or more second playback devices, wherein the first playback queue comprises the curated playlist of audio tracks, and wherein a second user account of the first cloud service is associated with the first media playback system; based on receiving the data indicating the instruction to share the first playback queue with the second media playback system, determining (i) whether the first user account of the first cloud service is a subscriber to the first cloud service and (ii) whether the second user account of the first cloud service is a subscriber to the first cloud service; and based on (a) determining that the first user account is a subscriber to the first cloud service and (b) determining that the second user account of the first cloud service is not a subscriber to the first cloud service, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each audio track in the first playback queue to a second playback queue for playback via the one or more second playback devices of the second media playback system, wherein the second playback queue defines a playback sequence for media items in the second playback queue, and (ii) apply a share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system causes the one or more second playback devices to have limited access according to the share restriction to the audio tracks within the curated playlist that are queued in the second playback queue, and wherein access to other audio tracks in the second playback queue is not limited according to the share restriction.
 2. The method of claim 1, further comprising: receiving, via the network interface of the first media playback system, data indicating an instruction to share the first playback queue with a third media playback system that comprises one or more third playback devices, wherein a third user account of the first cloud service is associated with the third media playback system; based on receiving the data indicating the instruction to share the first playback queue with the second media playback system, determining (i) whether the first user account of the first cloud service is a subscriber to the first cloud service and (ii) whether the third user account of the first cloud service is a subscriber to the first cloud service; and based on (a) determining that the first user account is a subscriber to the first cloud service and (b) determining that the third user account of the first cloud service is a subscriber to the first cloud service, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each audio track in the first playback queue to a third playback queue for playback via the one or more third playback devices of the third media playback system, wherein the third playback queue defines a playback sequence for media items in the third playback queue, and (ii) forego applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the third playback queue of the third media playback system.
 3. The method of claim 1, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system comprises assigning a playback restriction to prevent playback of audio tracks within the curated playlist that are queued in the second playback queue by the one or more second playback devices of the second media playback system.
 4. The method of claim 1, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system comprises assigning a modification restriction to prevent modification of an order of the second playback queue.
 5. The method of claim 1, wherein the first cloud service comprises multiple first cloud servers configured to provide a media playback system cloud service to a plurality of media playback systems, and wherein the second cloud service comprises multiple second cloud servers configured to provide a streaming audio cloud service.
 6. The method of claim 5, wherein the first media playback system comprises one or more servers of the media playback system cloud service.
 7. The method of claim 1, wherein the first cloud service comprises multiple first cloud servers configured to provide a playlist curation service that provides curated playlists from one or more additional cloud services comprising the second cloud service, and wherein the second cloud service comprises multiple second cloud servers configured to provide a streaming audio cloud service.
 8. The method of claim 1, further comprising: after sending the one or more instructions to apply the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system, receiving, via the network interface from the mobile device, instructions to add additional audio tracks to the first playback queue; based on the receiving the instructions to add additional audio tracks to the first playback queue, (i) adding respective representations of each additional audio track to the first playback queue, wherein the respective representations of each additional audio track within the curated playlist indicate respective network locations of each additional audio track and (ii) determining whether the first playback queue has been modified beyond a pre-determined modification threshold indicating a degree of similarity between the curated playlist of audio tracks and the first playback queue; and based on (a) receiving the instructions to add additional audio tracks to the first playback queue and (b) determining that the first playback queue has been modified beyond the pre-determined modification threshold, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each additional audio track in the first playback queue to the second playback queue for playback via the one or more second playback devices of the second media playback system and (ii) remove the share restriction from the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system.
 9. The method of claim 8, wherein determining whether the first playback queue has been modified beyond the pre-determined modification threshold indicating the degree of similarity between the curated playlist of audio tracks and the first playback queue comprises determining whether the additional audio tracks added to the first playback queue to alter the proprietary set of audio tracks defined and arranged into the particular sequence by the first cloud service beyond the pre-determined modification threshold.
 10. The method of claim 8, wherein the particular streaming audio service is a first streaming audio service, and wherein the second media playback system has access to the audio tracks within the curated playlist that are queued in the second playback queue from a third cloud service, and wherein the one or more second playback devices play back the audio tracks within the curated playlist that are queued in the second playback queue from the third cloud service after the share restriction is removed.
 11. A system comprising: one or more processors; a network interface; and data storage having instructions stored therein that are executable by the system to cause the system to perform functions comprising receiving, via the network interface from a mobile device, data representing an instruction to queue a curated playlist of audio tracks to a first playback queue for playback via one or more first playback devices of a first media playback system, wherein the first playback queue defines a playback sequence for media items in the first playback queue, wherein a first user account of a first cloud service is associated with the first media playback system, wherein the curated playlist of audio tracks consists of a proprietary set of audio tracks defined and arranged into a particular sequence by the first cloud service, and wherein the audio tracks of the curated playlist are streamable from one or more servers of a second cloud service; based on receiving the data representing an instruction to queue the curated playlist of audio tracks to the first playback queue, adding, via the first media playback system, respective representations of each audio track within the curated playlist to the first playback queue, wherein the first playback queue is maintained in data storage of the one or more first playback devices, and wherein the respective representations of each audio track within the curated playlist indicate respective network locations of each audio track at the one or more servers of the second cloud service; receiving, via the network interface of the first media playback system, data indicating an instruction to share the first playback queue with a second media playback system that comprises one or more second playback devices, wherein the first playback queue comprises the curated playlist of audio tracks, and wherein a second user account of the first cloud service is associated with the first media playback system; based on receiving the data indicating the instruction to share the first playback queue with the second media playback system, determining (i) whether the first user account of the first cloud service is a subscriber to the first cloud service and (ii) whether the second user account of the first cloud service is a subscriber to the first cloud service; and based on (a) determining that the first user account is a subscriber to the first cloud service and (b) determining that the second user account of the first cloud service is not a subscriber to the first cloud service, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each audio track in the first playback queue to a second playback queue for playback via the one or more second playback devices of the second media playback system, wherein the second playback queue defines a playback sequence for media items in the second playback queue, and (ii) apply a share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system causes the one or more second playback devices to have limited access according to the share restriction to the audio tracks within the curated playlist that are queued in the second playback queue, and wherein access to other audio tracks in the second playback queue is not limited according to the share restriction.
 12. The system of claim 11, wherein the functions further comprise: receiving, via the network interface of the first media playback system, data indicating an instruction to share the first playback queue with a third media playback system that comprises one or more third playback devices, wherein a third user account of the first cloud service is associated with the third media playback system; based on receiving the data indicating the instruction to share the first playback queue with the second media playback system, determining (i) whether the first user account of the first cloud service is a subscriber to the first cloud service and (ii) whether the third user account of the first cloud service is a subscriber to the first cloud service; and based on (a) determining that the first user account is a subscriber to the first cloud service and (b) determining that the third user account of the first cloud service is a subscriber to the first cloud service, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each audio track in the first playback queue to a third playback queue for playback via the one or more third playback devices of the third media playback system, wherein the third playback queue defines a playback sequence for media items in the third playback queue, and (ii) forego applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the third playback queue of the third media playback system.
 13. The system of claim 11, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system comprises assigning a playback restriction to prevent playback of audio tracks within the curated playlist that are queued in the second playback queue by the one or more second playback devices of the second media playback system.
 14. The system of claim 11, wherein applying the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system comprises assigning a modification restriction to prevent modification of an order of the second playback queue.
 15. The system of claim 11, wherein the first cloud service comprises multiple first cloud servers configured to provide a media playback system cloud service to a plurality of media playback systems, and wherein the second cloud service comprises multiple second cloud servers configured to provide a streaming audio cloud service.
 16. The system of claim 15, wherein the first media playback system comprises one or more servers of the media playback system cloud service.
 17. The system of claim 11, wherein the first cloud service comprises multiple first cloud servers configured to provide a playlist curation service that provides curated playlists from one or more additional cloud services comprising the second cloud service, and wherein the second cloud service comprises multiple second cloud servers configured to provide a streaming audio cloud service.
 18. The system of claim 11, wherein the functions further comprise: after sending the one or more instructions to apply the share restriction to the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system, receiving, via the network interface from the mobile device, instructions to add additional audio tracks to the first playback queue; based on the receiving the instructions to add additional audio tracks to the first playback queue, (i) adding respective representations of each additional audio track to the first playback queue, wherein the respective representations of each additional audio track within the curated playlist indicate respective network locations of each additional audio track and (ii) determining whether the first playback queue has been modified beyond a pre-determined modification threshold indicating a degree of similarity between the curated playlist of audio tracks and the first playback queue; and based on (a) receiving the instructions to add additional audio tracks to the first playback queue and (b) determining that the first playback queue has been modified beyond the pre-determined modification threshold, sending, via the network interface of the first media playback system to the second media playback system, one or more instructions to (i) add respective representations of each additional audio track in the first playback queue to the second playback queue for playback via the one or more second playback devices of the second media playback system and (ii) remove the share restriction from the respective representations of the audio tracks within the curated playlist that are queued in the second playback queue of the second media playback system.
 19. The system of claim 18, wherein determining whether the first playback queue has been modified beyond the pre-determined modification threshold indicating the degree of similarity between the curated playlist of audio tracks and the first playback queue comprises determining whether the additional audio tracks added to the first playback queue to alter the proprietary set of audio tracks defined and arranged into the particular sequence by the first cloud service beyond the pre-determined modification threshold.
 20. The system of claim 18, wherein the particular streaming audio service is a first streaming audio service, and wherein the second media playback system has access to the audio tracks within the curated playlist that are queued in the second playback queue from a third cloud service, and wherein the one or more second playback devices play back the audio tracks within the curated playlist that are queued in the second playback queue from the third cloud service after the share restriction is removed. 